Skip to content

Remove Manager McTest references from frontend#91084

Merged
MonilBhavsar merged 9 commits into
mainfrom
claude-removeManagerMcTest
May 25, 2026
Merged

Remove Manager McTest references from frontend#91084
MonilBhavsar merged 9 commits into
mainfrom
claude-removeManagerMcTest

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

@MelvinBot MelvinBot commented May 19, 2026

Explanation of Change

Manager McTest is no longer supported on the backend. This PR removes all frontend references to Manager McTest, including:

  • Constants: EMAIL.MANAGER_MCTEST, BETAS.NEWDOT_MANAGER_MCTEST, ACCOUNT_ID.MANAGER_MCTEST, and exclusion list entries
  • Utility functions: isSelectedManagerMcTest(), isTestTransactionReport(), getManagerMcTestParticipant(), isManagerMcTestQuickActionReport(), getRestrictedLogins()
  • Special handling: Manager McTest overrides in buildOptimisticIOUReportAction, buildOptimisticReportPreview, getMoneyRequestOptions, shouldDisableThread, money request builder flows, scan receipt participant routing, Quick Action Bar restrictions, and participant search filtering
  • Tests: Removed all Manager McTest-specific test cases and fixtures

Fixed Issues

$ #91068

Tests

  1. Create an expense (Submit flow)

    • Open the app, tap the + FAB > Submit expense
    • Scan a receipt or enter an amount manually
    • Select a participant and submit the expense
    • Verify the expense is created successfully with no errors
  2. Create an expense (Split flow)

    • Open the app, tap + FAB > Split expense
    • Add participants, enter amount, and split
    • Verify the split is created with no errors
  3. Duplicate expense action

    • Find an existing expense, open the secondary actions menu
    • Tap Duplicate
    • Verify the duplicate action works correctly
  4. Quick Action Bar

    • Navigate to a DM chat
    • Verify the Quick Action Bar appears and all quick actions (Submit, Track, etc.) function correctly
    • Verify no errors in the console
  5. Search participants

    • Start creating a new expense
    • On the participant search screen, search for various users
    • Verify Expensify system accounts (Concierge, etc.) behave as expected — no unexpected accounts appear
  6. Thread creation

    • Open an expense report action
    • Verify threading works normally on expense report actions
  7. Verify no console errors

    • Perform all the above flows while monitoring the JS console
    • Verify no errors appear related to Manager McTest or missing references

Offline tests

N/A — this is a code removal PR with no new offline behavior.

QA Steps

  1. Create a new Submit expense (scan a receipt) on a personal account with no workspace — verify it works end-to-end
  2. Create a new Submit expense with a manual amount — verify it works
  3. Open an existing expense and use the Duplicate action — verify it works
  4. Check Quick Action Bar on a DM chat — verify quick actions appear and work
  5. Start a new expense and search for participants — verify the search works correctly
  6. Verify no JS console errors throughout all flows

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Screen.Recording.2026-05-25.at.6.08.39.PM.mov
Android: mWeb Chrome
Screen.Recording.2026-05-25.at.5.33.26.PM.mov
iOS: Native
Screen.Recording.2026-05-25.at.5.31.17.PM.mov
iOS: mWeb Safari
Screen.Recording.2026-05-25.at.5.29.19.PM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-05-25.at.5.34.31.PM.mov

Manager McTest is no longer supported on the backend. This removes all
frontend references including constants, utility functions, special
handling in money request flows, Quick Action Bar restrictions, and
participant filtering logic.

Co-authored-by: Ishpaul Singh <ishpaul777@users.noreply.github.com>
…Policy and spy canCreateRequest

The per diem test mocked isPaidGroupPolicy but the source code calls isControlPolicy.
Both per diem and time tracking positive tests also need canCreateRequest mocked since
the minimal test data doesn't satisfy the real canCreateRequest conditions.

Co-authored-by: Ishpaul Singh <ishpaul777@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Fixed the failing QuickActionUtilsTest check:

  1. Per diem test mocked isPaidGroupPolicy but the source code calls isControlPolicy — corrected the mock target.
  2. Both per diem and time tracking positive tests needed canCreateRequest spied to return true, since the minimal stub data doesn't satisfy the real canCreateRequest conditions.

All 11 tests now pass.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 19, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 93.84% <ø> (-0.05%) ⬇️
src/hooks/useSearchBulkActions.ts 47.93% <ø> (ø)
src/libs/OptionsListUtils/index.ts 84.51% <100.00%> (-0.19%) ⬇️
src/libs/QuickActionUtils.ts 31.91% <ø> (-4.45%) ⬇️
src/libs/ReportUtils.ts 83.08% <100.00%> (+0.04%) ⬆️
src/libs/actions/IOU/MoneyRequest.ts 76.49% <100.00%> (-0.43%) ⬇️
src/libs/actions/IOU/MoneyRequestBuilder.ts 87.60% <100.00%> (+3.45%) ⬆️
src/pages/iou/request/ParticipantSearchResults.tsx 0.66% <ø> (+0.02%) ⬆️
...es/iou/request/step/IOURequestStepConfirmation.tsx 66.56% <100.00%> (-0.11%) ⬇️
...RequestStepScan/components/MobileWebCameraView.tsx 0.00% <ø> (ø)
... and 2 more
... and 7 files with indirect coverage changes

MelvinBot and others added 2 commits May 19, 2026 14:33
…cTest

Co-authored-by: Ishpaul Singh <ishpaul777@users.noreply.github.com>
…tead of policy ID string

After merging main, the new shouldRestrictUserBillableActions calls from
PR \#88363 were passing defaultExpensePolicy.id (a string) where the
function expects OnyxEntry<Policy>. This fixes all 5 call sites.

Co-authored-by: Ishpaul Singh <ishpaul777@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Fixed the failing typecheck: after merging main, the new shouldRestrictUserBillableActions calls from #88363 were passing defaultExpensePolicy.id (a string) where the function expects OnyxEntry<Policy>. Updated all 5 call sites to pass the full policy object instead.

…t removal

Co-authored-by: Ishpaul Singh <ishpaul777@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Fixed the failing ESLint checks: removed unused imports and variables left over from the Manager McTest removal (getChatByParticipants in OptionsListUtils, deprecatedCurrentUserPersonalDetails and personalDetails in MoneyRequestBuilder, ReportUtils in MoneyRequestTest).

The Jest failure in QuickActionUtilsTest is pre-existing (fails on main) and unrelated to this PR.

@ishpaul777
Copy link
Copy Markdown
Contributor

@MelvinBot the action are not running please run those

@MelvinBot
Copy link
Copy Markdown
Contributor Author

The CI actions are already running — all checks currently show pending status, meaning they've been triggered and are in progress. Give them a few minutes to complete. You can monitor progress here: https://github.com/Expensify/App/pull/91084/checks

@MelvinBot
Copy link
Copy Markdown
Contributor Author

⚠️ MelvinBot CI Fix Loop Detected

MelvinBot has made 5 consecutive commits trying to fix CI failures. Automatic CI fix dispatches are now paused for this PR.

Next steps: A human should review the recent commits and resolve the conflicting CI errors manually.

@ishpaul777
Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. What shall we delve into next?

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@ishpaul777
Copy link
Copy Markdown
Contributor

@MelvinBot please make it ready for review

@MelvinBot MelvinBot marked this pull request as ready for review May 21, 2026 16:47
@MelvinBot MelvinBot requested a review from a team as a code owner May 21, 2026 16:47
@MelvinBot
Copy link
Copy Markdown
Contributor Author

PR has been marked as ready for review as requested.

Note: The Tests and QA Steps sections in the PR description still contain TODO placeholders — please fill those in so reviewers have testing context.

@melvin-bot melvin-bot Bot requested review from joekaufmanexpensify and linhvovan29546 and removed request for a team May 21, 2026 16:47
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 21, 2026

@linhvovan29546 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@ishpaul777
Copy link
Copy Markdown
Contributor

@MelvinBot please suggest testing steps for this and add it in PR description

@MelvinBot
Copy link
Copy Markdown
Contributor Author

Updated the PR description with suggested testing steps covering the key areas affected by the Manager McTest removal:

  1. Submit expense — ensures the core expense creation flow still works without Manager McTest participant routing
  2. Split expense — validates split flow is unaffected
  3. Duplicate action — tests the shouldRestrictUserBillableActions signature change
  4. Quick Action Bar — confirms QAB no longer has Manager McTest restrictions
  5. Participant search — verifies Manager McTest no longer appears in search results
  6. Thread creation — ensures threading on expense actions works without the Manager McTest thread-disable logic
  7. Console error check — catch any missing references

Please review and adjust as needed before testing.

@ishpaul777
Copy link
Copy Markdown
Contributor

ishpaul777 commented May 21, 2026

@MelvinBot a few things to address before this is ready:

  1. Leftover Manager McTest references not cleaned up Two references were missed:
  • src/types/onyx/Transaction.ts - the JSDoc still says Receipt is manager_mctest@expensify.com testing receipt. The isTestReceipt field itself is still used by useReceiptTraining, ReceiptFileValidator, etc. for the receipt-training tooltip / CONST.TEST_RECEIPT flow, so the field can stay, but please update the comment so it no longer references Manager McTest.
  • .env.example line 38 - EXPENSIFY_ACCOUNT_ID_MANAGER_MCTEST=-1 is dangling now that CONST.ACCOUNT_ID.MANAGER_MCTEST was removed. Please delete that line.
  1. Unrelated change bundled in
    The PR also rewrites 5 call sites of shouldRestrictUserBillableActions from (defaultExpensePolicy.id, ...) to (defaultExpensePolicy, ...) in MoneyRequestHeaderSecondaryActions.tsx, useExpenseActions.ts, and useSearchBulkActions.ts. This is a typecheck fix forced by #88363 after the merge with main and is unrelated to Manager McTest removal. please check if its already fixed on main and sync main

- Update JSDoc comment on isTestReceipt in Transaction.ts (remove manager_mctest reference)
- Delete dangling EXPENSIFY_ACCOUNT_ID_MANAGER_MCTEST from .env.example
- Restore eslint-disable comment in useSearchBulkActions.ts (unrelated removal)

Co-authored-by: Ishpaul Singh <ishpaul777@users.noreply.github.com>
@ishpaul777
Copy link
Copy Markdown
Contributor

Yeah, I mean deleting it from the db

i'll start a conversation with team having access to DB, can you please continue review?

@linhvovan29546
Copy link
Copy Markdown
Contributor

@ishpaul777 Could you please ask Melvin to merge the main branch to resolve the failing check?

Copy link
Copy Markdown
Contributor

@linhvovan29546 linhvovan29546 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@linhvovan29546
Copy link
Copy Markdown
Contributor

The PR author checklist should be resolved manually, like in this discussion. https://expensify.slack.com/archives/C02NK2DQWUX/p1779455069201039

Comment thread src/hooks/useSearchBulkActions.ts Outdated
@@ -1,3 +1,4 @@
/* eslint-disable react-hooks/refs */
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ CONSISTENCY-5 (docs)

This file-level /* eslint-disable react-hooks/refs */ was added without a justification comment explaining why the rule is permanently suppressed for the entire file. eslint-disable comments hide violations from the seatbelt baseline and should only be used for permanent suppressions with a clear reason.

Either add a justification comment explaining why react-hooks/refs does not apply to this file, or if this is a temporary suppression, prefer widening the seatbelt baseline with SEATBELT_INCREASE instead. For example:

/* eslint-disable react-hooks/refs -- Refs in this hook are used inside callbacks that capture stable references; the lint rule flags false positives for these patterns */

Reviewed at: f069557 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merged main and added a justification comment to the eslint-disable directive: /* eslint-disable react-hooks/refs -- Refs in this hook are used inside callbacks that capture stable references; the lint rule flags false positives for these patterns */

@ishpaul777
Copy link
Copy Markdown
Contributor

@MelvinBot please sync main and address this comment #91084 (comment)

MelvinBot and others added 2 commits May 23, 2026 21:16
…cTest

Co-authored-by: Ishpaul Singh <ishpaul777@users.noreply.github.com>
Synced with main and added a justification comment to the
react-hooks/refs eslint-disable directive in useSearchBulkActions.ts
per review feedback.

Co-authored-by: Ishpaul Singh <ishpaul777@users.noreply.github.com>
@ishpaul777
Copy link
Copy Markdown
Contributor

@MelvinBot fix eslint

The import was left behind after removing Manager McTest code
that was the only consumer. This fixes the ESLint no-unused-vars error.

Co-authored-by: Ishpaul Singh <ishpaul777@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Fixed the ESLint failure: removed unused getCurrentUserPersonalDetails import from src/libs/actions/IOU/MoneyRequestBuilder.ts. It was left behind after the Manager McTest removal.

@ishpaul777
Copy link
Copy Markdown
Contributor

@MelvinBot please complete author checklist in PR description

@MelvinBot
Copy link
Copy Markdown
Contributor Author

Completed the author checklist. Since this is a code removal PR (no new files, no new CSS, no new assets, no UI changes, no deeplinks, no Storybook, no message editing code, no new pages), all conditional "If..." items were checked as N/A.

Items left unchecked for human verification:

  • Screenshots/videos on all platforms
  • Platform testing (Android Native/mWeb, iOS Native/mWeb, MacOS)
  • High Traffic account testing

@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 24, 2026

We did not find an internal engineer to review this PR, trying to assign a random engineer to #91068 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot melvin-bot Bot requested a review from MonilBhavsar May 24, 2026 02:17
Comment thread tests/unit/QuickActionUtilsTest.ts
@MonilBhavsar
Copy link
Copy Markdown
Contributor

@ishpaul777 @MelvinBot author checklist is failing

@linhvovan29546
Copy link
Copy Markdown
Contributor

@MonilBhavsar The PR author checklist should be resolved manually, like in this discussion. https://expensify.slack.com/archives/C02NK2DQWUX/p1779455069201039

@MonilBhavsar
Copy link
Copy Markdown
Contributor

Right, but @ishpaul777 needs to provide a description, no?

@linhvovan29546
Copy link
Copy Markdown
Contributor

Yes, we need to update it manually. Both of you can resolve that.

@ishpaul777
Copy link
Copy Markdown
Contributor

ishpaul777 commented May 25, 2026

@MonilBhavsar can you please replace it with below checklist, i cant edit PR description

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Screen.Recording.2026-05-25.at.6.08.39.PM.mov
Android: mWeb Chrome
Screen.Recording.2026-05-25.at.5.33.26.PM.mov
iOS: Native
Screen.Recording.2026-05-25.at.5.31.17.PM.mov
iOS: mWeb Safari
Screen.Recording.2026-05-25.at.5.29.19.PM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-05-25.at.5.34.31.PM.mov

Copy link
Copy Markdown
Contributor

@MonilBhavsar MonilBhavsar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks!

@MonilBhavsar MonilBhavsar merged commit ae7c8f1 into main May 25, 2026
62 of 64 checks passed
@MonilBhavsar MonilBhavsar deleted the claude-removeManagerMcTest branch May 25, 2026 13:15
@github-actions
Copy link
Copy Markdown
Contributor

🚧 @MonilBhavsar has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify
Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants